Multiple software versions in a switch group

ABSTRACT

One embodiment of the present invention provides a switch. The switch includes one or more ports, a switch group module, a persistent storage module, and a synchronization module. The switch group module maintains a membership in a switch group. The persistent storage module stores configuration information associated with the switch group in a data structure, which includes one or more columns for attribute values of the configuration information, in a local persistent storage. The synchronization module obtains update information, which includes a first set of attribute values, from a portable representation. The synchronization module identifies a software version of a second switch in the switch group and generates an update instruction to update the first data structure in a persistent storage in the second switch with target update information. The target update information comprises a second set of attribute values updated from the first set of attribute values.

RELATED APPLICATION

The present disclosure is related to U.S. Pat. No. 8,867,552, titled “Virtual Cluster Switching,” by inventors Suresh Vobbilisetty and Dilip Chatwani, issued 21 Oct. 2014; and U.S. patent application Ser. No. 14/512,268, titled “Distributed Configuration Management in a Switch Group,” by inventors Vidyasagara R. Guntaka, Suresh Vobbilisetty, Manjunath A. G. Gowda, and Himanshu Varshney, filed 10 Oct. 2014, the disclosures of which are incorporated by reference herein.

BACKGROUND

Field

The present disclosure relates to communication networks. More specifically, the present disclosure relates to a method for a constructing a scalable, multi-version system.

Related Art

The exponential growth of the Internet has made it a popular delivery medium for a variety of applications running on physical and virtual devices. Such applications have brought with them an increasing demand for bandwidth. As a result, equipment vendors race to build larger and faster switches with versatile capabilities. However, the size of a switch cannot grow infinitely. It is limited by physical space, power consumption, and design complexity, to name a few factors. Furthermore, switches with higher capability are usually more complex and expensive. More importantly, because an overly large and complex system often does not provide economy of scale, simply increasing the size and capability of a switch may prove economically unviable due to the increased per-port cost.

A flexible way to improve the scalability of a switch system is to build a fabric switch. A fabric switch is a collection of individual member switches. These member switches form a single, logical switch that can have an arbitrary number of ports and an arbitrary topology. As demands grow, customers can adopt a “pay as you grow” approach to scale up the capacity of the fabric switch. However, these member switches typically have the same software version to operate as a single switch. As a result, a switch with an updated software version may not operate as a member switch with switches with an older software version. Hence, a software version update may not be performed gradually while keeping a respective member switch operational in the fabric switch.

Meanwhile, a switch, an individual or a member switch of a fabric switch, continues to store more configuration information as the switch participates in network virtualizations, partitions, and switch groups, and operates on a plurality of network protocols of different network layers. This configuration needs to be applied to the switch when the switch powers up, and thus, should be persistent. A switch typically stores such configuration information in a local storage in an unstructured format. The switch reads the information during booting up (i.e., powering up), and loads the information into memory. Managing persistent storage in unstructured format is inefficient and requires runtime structuring.

While persistent storage brings many desirable features to a switch, some issues remain unsolved in efficiently facilitating interoperability of multiple software versions in a switch group.

SUMMARY

One embodiment of the present invention provides a first switch. The first switch includes one or more ports, a switch group module, a persistent storage module, and a synchronization module. The switch group module maintains a membership in a switch group. The switch group includes a plurality of switches and operates as a single switch. The persistent storage module stores configuration information associated with the switch group in a data structure, which includes one or more columns for attribute values of the configuration information, in a local persistent storage. The synchronization module obtains update information from a portable representation. This update information comprises a first set of attribute values for a first data structure in the persistent storage. The synchronization module identifies a software version of a second switch in the switch group and generates an update instruction to update the first data structure in a persistent storage in the second switch with target update information. The target update information comprises a second set of attribute values updated from the first set of attribute values.

In a variation on this embodiment, the software version of the second switch is the same as the first switch, and wherein the first and second sets of attribute values are the same.

In a variation on this embodiment, the synchronization module identifies the software version of the second switch from a mapping between an identifier of the second switch and the software version.

In a variation on this embodiment, the synchronization module verifies whether the target update information is prepared for storage in a persistent storage of a respective switch of the switch group. If the update information is prepared, the synchronization module generates an instruction message instructing to commit the target update information to the persistent storage and switch modules of a respective switch of the switch group.

In a further variation, if the update information is not prepared, the synchronization module rolls back the target update information from a persistent storage of a switch, which has succeeded in storage preparation, of the switch group.

In a variation on this embodiment, the first switch also includes a conversion module which converts a first attribute value to a second attribute value. The first attribute value is of a first attribute type and is in the first set of attribute values, and the second attribute value is of a second attribute type and is in the second set of attribute values.

In a variation on this embodiment, the first switch also includes a conversion module which assigns a default attribute value to an attribute in the target update information.

In a variation on this embodiment, the persistent storage is an object relational database, and a data structure in the persistent storage is a table in the database.

In a variation on this embodiment, the portable representation is based on one or more of: Extensible Markup Language (XML) and JavaScript Object Notation (JSON).

In a variation on this embodiment, the switch group is an Ethernet fabric switch, wherein the plurality of switches included the switch group operate as a single Ethernet switch.

One embodiment of the present invention provides a switch. The switch includes one or more ports, a switch group module, a persistent storage module, and a synchronization module. The switch group module maintains a membership in a switch group. The switch group includes a plurality of switches and operates as a single switch. The persistent storage module stores configuration information associated with the switch group in a table, which includes one or more columns for attribute values of the configuration information, in a local persistent storage. The synchronization module identifies update information from a received user command. The update information comprises a first set of attribute values for a first data structure in the persistent storage. The synchronization module generates a portable representation of the received update information and generates a notification message comprising the portable representation. This notification message is destined for a second switch in the switch group.

In a variation on this embodiment, the synchronization module verifies whether the update information is prepared for storage in the persistent storage. If the update information is prepared, the synchronization module generates an acknowledgement message comprising a transaction identifier associated with the preparation.

In a variation on this embodiment, the portable representation is based on one or more of: Extensible Markup Language (XML) and JavaScript Object Notation (JSON).

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1A illustrates an exemplary network with persistent storage framework support, in accordance with an embodiment of the present invention.

FIG. 1B illustrates an exemplary persistent storage framework support in a switch, in accordance with an embodiment of the present invention.

FIG. 2 illustrates an exemplary object identifier generated by a persistent storage framework in a switch, in accordance with an embodiment of the present invention.

FIG. 3 illustrates exemplary base classes for supporting a persistent storage framework in a switch, in accordance with an embodiment of the present invention.

FIG. 4A illustrates an exemplary Unified Modeling Language (UML) model of classes of a switch with a persistent storage framework, in accordance with an embodiment of the present invention.

FIG. 4B illustrates an exemplary Extensible Markup Language (XML) representation of a class corresponding to a switch with a persistent storage framework, in accordance with an embodiment of the present invention.

FIG. 4C illustrates exemplary tables generated by a persistent storage framework in a switch, in accordance with an embodiment of the present invention.

FIG. 4D illustrates an exemplary table representing a one-to-many association, which is generated by in a persistent storage framework in a switch, in accordance with an embodiment of the present invention.

FIG. 5A presents a flowchart illustrating the process of a persistent storage framework of a switch generating auxiliary tables for an inheritance chain in a persistent storage, in accordance with an embodiment of the present invention.

FIG. 5B presents a flowchart illustrating the process of a persistent storage framework of a switch generating class tables in a persistent storage, in accordance with an embodiment of the present invention.

FIG. 5C presents a flowchart illustrating the process of a persistent storage framework of a switch generating an auxiliary table representing an one-to-many relationship in a persistent storage, in accordance with an embodiment of the present invention.

FIG. 5D presents a flowchart illustrating the process of a persistent storage framework of a switch updating tables in a persistent storage, in accordance with an embodiment of the present invention.

FIG. 6A illustrates an exemplary network with persistent storage framework and distributed configuration management support, in accordance with an embodiment of the present invention.

FIG. 6B illustrates an exemplary switch group with multi-input and multi-principal switch support, in accordance with an embodiment of the present invention.

FIG. 7A illustrates an exemplary switch group with persistent storage framework and multiple software versions, in accordance with an embodiment of the present invention.

FIG. 7B illustrates exemplary XML representations of update information for multiple software versions, in accordance with an embodiment of the present invention.

FIG. 7C illustrates an exemplary synchronization management among switches with different software versions, in accordance with an embodiment of the present invention.

FIG. 8A presents a flowchart illustrating the synchronization process of a managed switch with persistent storage framework, in accordance with an embodiment of the present invention.

FIG. 8B presents a flowchart illustrating the synchronization process of a principal switch with persistent storage framework, in accordance with an embodiment of the present invention.

FIG. 8C presents a flowchart illustrating the process of a principal switch generating update information for a target software version for the synchronization process, in accordance with an embodiment of the present invention.

FIG. 9 illustrates an exemplary switch with a persistent storage framework and interoperability with multiple software versions, in accordance with an embodiment of the present invention.

In the figures, like reference numerals refer to the same figure elements.

DETAILED DESCRIPTION

The following description is presented to enable any person skilled in the art to make and use the invention, and is provided in the context of a particular application and its requirements. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present invention. Thus, the present invention is not limited to the embodiments shown, but is to be accorded the widest scope consistent with the claims.

Overview

In embodiments of the present invention, the problem of incorporating multiple software versions in a switch group is solved by using portable representation of configuration information and converting the attribute values in the portable representation to corresponding attribute values of an appropriate software version. A software version can indicate, but is not limited to, the version of the operating system, one or more applications, switch images, persistent storage framework, and/or plug-ins of the persistent storage framework. A switch in the switch group can be referred to as a member switch.

With existing technologies, a switch can be configured by logging in to the switch (e.g., via telnet) or via a console port (e.g., an RS-232 port). Such configuration can be related to network virtualizations, partitions, and switch groups, and a plurality of network protocols of different network layers. The attribute values (e.g., parameters) of the configuration information are applied to the switch (e.g., loaded to the switch modules). In some embodiments, one of the switches in the switch group is elected as a principal switch, which manages and distributes configuration information in the switch group. The rest of the switches of the switch group can be referred to as managed switches. When a user accesses this principal switch, the principal switch allows the user to configure the global configuration information of the switch group. The principal switch, in turn, synchronizes that global configuration information with a respective managed switch. Furthermore, the principal switch also allows the user to configure a respective managed switch in the switch group. The principal switch, in turn, synchronizes that local configuration information to that managed switch.

Typically, to facilitate synchronization among the member switches, the member switches of a switch group have the same software version (e.g., software version). This causes a switch with an upgraded software version to leave the switch group until other switches are upgraded as well. For example, an attribute type in the configuration information can be different for different software versions. As a result, when the principal switch tries to synchronize the value of the attribute, an inconsistency can occur among the switches with different software versions. Hence, a software version upgrade may not be performed gradually while keeping a respective member switch operational in the switch group. This leads to unavailability and reduced operational capability of the switch group.

To solve this problem, a respective switch of the switch group uses a portable representation (e.g., an XML representation) to send its update information to the principal switch. The information in a portable representation is recognizable by the principal switch of a switch group. Examples of update information include, but are not limited to, an update to global or local configuration information (e.g., an updated attribute value), a new configuration (e.g., a new VLAN), a new switch image, and a new database image e.g., a database dump). Upon receiving the update information from a user (e.g., a network administrator) via a user command, a member switch sends the update information to the principal switch in the portable representation. The principal switch extracts the update information from the portable representation and creates an instruction to update the corresponding attributes with the received attribute values in the portable representation for a respective software version in the switch group. The principal switch then sends the instruction for a software version to the managed switches with that software version.

In some embodiments, the principal switch supports type conversion. If an attribute type (e.g., an IP address) in a software version is different than the attribute type (e.g., an integer) of the switch version of the originating switch, the principal switch, if supported, can convert the attribute types (e.g., from integer to IP address). Otherwise, the principal switch uses a default value for that different attribute type (e.g., a default IP address). In this way, the configuration information of a respective member switch, even with different software versions, remains synchronized, thereby facilitating interoperability in the switch group.

In some embodiments, a respective switch of the switch group is equipped with a persistent storage framework which stores the configuration information in a local persistent storage. Such a persistent storage can be an object relational database. The configuration information is loaded from this persistent storage to the switch modules (e.g., the application-specific integrated circuit (ASIC) chips of the switch). The principal switch maintains the global configuration information of the switch group and respective local configuration information of a respective switch in its local persistent storage. The principal switch provides a copy of its local persistent storage to a respective managed switch, which in turn, stores that copy in its local persistent storage. In this way, a respective switch in the switch group has the same local and global configuration information. This allows a user to access the configuration information of the switch group from any member switch. In this disclosure, the description in conjunction with FIGS. 1-5 is associated with persistent storage in the switch; the description in conjunction with FIGS. 6A-6B is associated with distributed configuration management in a switch group; and the description in conjunction with FIG. 7 and onward provides more details on different software versions in a switch group.

In some embodiments, the framework supports Model Driven Architecture (MDA), Object Oriented Programming (OOP), and/or Model/View/Controller (MVC) design patterns to facilitate modular development and operation of the units. The framework can also support class frameworks based on Unified Modeling Language (UML). Upon receiving class models (e.g., class name, attributes, and methods) and their relations based on UML, the framework automatically generates the corresponding code, thereby ensuring structure in the operational units of a switch. In some embodiments, the class models are expressed in YANG, which is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF).

Since the units operate on the framework in a modular way, their associated attribute values can be stored in a persistent storage in a structured way. In some embodiments, the framework uses Object-Relational Mapping to store the attribute values of the units in a structured way in an object relational database. The framework allows different classes to be defined for a unit based on MDA, OOP, and/or MVC design patterns. The framework then seamlessly maps a respective class to a database table and vice-versa. Furthermore, the framework also seamlessly represents the relationships among the classes (e.g., an association or a composition) in the database. As a result, when a unit becomes operational on the switch, attribute values associated with a respective class in that unit is automatically loaded from the database. Moreover, if a class changes (e.g., a new attribute or a new relationship), the framework seamlessly incorporates that change into the database.

In some embodiments, the switch group can be a fabric switch. The switch can include one or more units which allow the switch to join and operate as a member switch of the fabric switch. These units can also run on the framework. In a fabric switch, any number of switches coupled in an arbitrary topology may logically operate as a single switch. The fabric switch can be an Ethernet fabric switch or a virtual cluster switch (VCS), which can operate as a single Ethernet switch. Any member switch may join or leave the fabric switch in “plug-and-play” mode without any manual configuration. In some embodiments, a respective switch in the fabric switch is a Transparent Interconnection of Lots of Links (TRILL) routing bridge (RBridge). In some further embodiments, a respective switch in the fabric switch is an Internet Protocol (IP) routing-capable switch (e.g., an IP router).

It should be noted that a fabric switch is not the same as conventional switch stacking. In switch stacking, multiple switches are interconnected at a common location (often within the same rack), based on a particular topology, and manually configured in a particular way. These stacked switches typically share a common address, e.g., an IP address, so they can be addressed as a single switch externally. Furthermore, switch stacking requires a significant amount of manual configuration of the ports and inter-switch links. The need for manual configuration prohibits switch stacking from being a viable option in building a large-scale switching system. The topology restriction imposed by switch stacking also limits the number of switches that can be stacked. This is because it is very difficult, if not impossible, to design a stack topology that allows the overall switch bandwidth to scale adequately with the number of switch units.

In contrast, a fabric switch can include an arbitrary number of switches with individual addresses, can be based on an arbitrary topology, and does not require extensive manual configuration. The switches can reside in the same location, or be distributed over different locations. These features overcome the inherent limitations of switch stacking and make it possible to build a large “switch farm,” which can be treated as a single, logical switch. Due to the automatic configuration capabilities of the fabric switch, an individual physical switch can dynamically join or leave the fabric switch without disrupting services to the rest of the network.

Furthermore, the automatic and dynamic configurability of the fabric switch allows a network operator to build its switching system in a distributed and “pay-as-you-grow” fashion without sacrificing scalability. The fabric switch's ability to respond to changing network conditions makes it an ideal solution in a virtual computing environment, where network loads often change with time.

In switch stacking, multiple switches are interconnected at a common location (often within the same rack), based on a particular topology, and manually configured in a particular way. These stacked switches typically share a common address, e.g., an IP address, so they can be addressed as a single switch externally. Furthermore, switch stacking requires a significant amount of manual configuration of the ports and inter-switch links. The need for manual configuration prohibits switch stacking from being a viable option in building a large-scale switching system. The topology restriction imposed by switch stacking also limits the number of switches that can be stacked. This is because it is very difficult, if not impossible, to design a stack topology that allows the overall switch bandwidth to scale adequately with the number of switch units.

It should also be noted that a fabric switch is distinct from a virtual local area network (VLAN). A fabric switch can accommodate a plurality of VLANs. A VLAN is typically identified by a VLAN tag. In contrast, the fabric switch is identified a fabric identifier (e.g., a VCS identifier), which is assigned to the fabric switch. A respective member switch of the fabric switch is associated with the fabric identifier. Furthermore, when a member switch of a fabric switch learns a media access control (MAC) address of an end device (e.g., via layer-2 MAC address learning), the member switch generates a notification message, includes the learned MAC address in the payload of the notification message, and sends the notification message to all other member switches of the fabric switch. In this way, a learned MAC address is shared among a respective member switch of the fabric switch.

The term “fabric switch” refers to a number of interconnected physical switches which form a single, scalable logical switch. These physical switches are referred to as member switches of the fabric switch. In a fabric switch, any number of switches can be connected in an arbitrary topology, and the entire group of switches functions together as one single, logical switch. This feature makes it possible to use many smaller, inexpensive switches to construct a large fabric switch, which can be viewed as a single logical switch externally. Although the present disclosure is presented using examples based on a fabric switch, embodiments of the present invention are not limited to a fabric switch. Embodiments of the present invention are relevant to any computing device that includes a plurality of devices operating as a single device.

The term “end device” can refer to any device external to a fabric switch. Examples of an end device include, but are not limited to, a host machine, a conventional layer-2 switch, a layer-3 router, or any other type of network device. Additionally, an end device can be coupled to other switches or hosts further away from a layer-2 or layer-3 network. An end device can also be an aggregation point for a number of network devices to enter the fabric switch. An end device hosting one or more virtual machines can be referred to as a host machine. In this disclosure, the terms “end device” and “host machine” are used interchangeably.

The term “switch” is used in a generic sense, and it can refer to any standalone or fabric switch operating in any network layer. “Switch” should not be interpreted as limiting embodiments of the present invention to layer-2 networks. Any device that can forward traffic to an external device or another switch can be referred to as a “switch.” Any physical or virtual device (e.g., a virtual machine/switch operating on a computing device) that can forward traffic to an end device can be referred to as a “switch.” Examples of a “switch” include, but are not limited to, a layer-2 switch, a layer-3 router, a TRILL RBridge, or a fabric switch comprising a plurality of similar or heterogeneous smaller physical and/or virtual switches.

The term “edge port” refers to a port on a fabric switch which exchanges data frames with a network device outside of the fabric switch (i.e., an edge port is not used for exchanging data frames with another member switch of a fabric switch). The term “inter-switch port” refers to a port which sends/receives data frames among member switches of a fabric switch. The terms “interface” and “port” are used interchangeably.

The term “switch identifier” refers to a group of bits that can be used to identify a switch. Examples of a switch identifier include, but are not limited to, a media access control (MAC) address, an Internet Protocol (IP) address, and an RBridge identifier. Note that the TRILL standard uses “RBridge ID” (RBridge identifier) to denote a 48-bit intermediate-system-to-intermediate-system (IS-IS) System ID assigned to an RBridge, and “RBridge nickname” to denote a 16-bit value that serves as an abbreviation for the “RBridge ID.” In this disclosure, “switch identifier” is used as a generic term, is not limited to any bit format, and can refer to any format that can identify a switch. The term “RBridge identifier” is also used in a generic sense, is not limited to any bit format, and can refer to “RBridge ID,” “RBridge nickname,” or any other format that can identify an RBridge.

The term “packet” refers to a group of bits that can be transported together across a network. “Packet” should not be interpreted as limiting embodiments of the present invention to layer-3 networks. “Packet” can be replaced by other terminologies referring to a group of bits, such as “message,” “frame,” “cell,” or “datagram.”

Network Architecture

FIG. 1A illustrates an exemplary network with persistent storage framework support, in accordance with an embodiment of the present invention. As illustrated in FIG. 1A, a network 100 includes switches 101, 102, 103, 104, and 105. An end device 112 is coupled to switch 102. In some embodiments, end device 112 is a host machine, hosting one or more virtual machines. End device 112 can include a hypervisor, which runs one or more virtual machines. End device 112 can be equipped with a Network Interface Card (NIC) with one or more ports. End device 112 couples to switch 102 via the ports of the NIC.

In some embodiments, network 100 is a TRILL network and a respective switch of network 100, such as switch 102, is a TRILL RBridge. Under such a scenario, communication among the switches in network 100 is based on the TRILL protocol. For example, upon receiving an Ethernet frame from end device 112, switch 102 encapsulates the received Ethernet frame in a TRILL header and forwards the TRILL packet. In some further embodiments, network 100 is an IP network and a respective switch of network 100, such as switch 102, is an IP-capable switch, which calculates and maintains a local IP routing table (e.g., a routing information base or RIB), and is capable of forwarding packets based on its IP addresses. Under such a scenario, communication among the switches in network 100 is based on IP. For example, upon receiving an Ethernet frame from end device 112, switch 102 encapsulates the received Ethernet frame in an IP header and forwards the IP packet.

In some embodiments, network 100 is a fabric switch (under such a scenario, network 100 can also be referred to as fabric switch 100). Fabric switch 100 is assigned with a fabric switch identifier. A respective member switch of fabric switch 100 is associated with that fabric switch identifier. This allows the member switch to indicate that it is a member of fabric switch 100. In some embodiments, whenever a new member switch joins fabric switch 100, the fabric switch identifier is automatically associated with that new member switch. Furthermore, a respective member switch of fabric switch 100 is assigned a switch identifier (e.g., an RBridge identifier, a Fibre Channel (FC) domain ID (identifier), or an IP address). This switch identifier identifies the member switch in fabric switch 100.

Switches in fabric switch 100 use edge ports to communicate with end devices (e.g., non-member switches) and inter-switch ports to communicate with other member switches. For example, switch 102 is coupled to end device 112 via an edge port and to switches 101, 103, 104, and 105 via inter-switch ports and one or more links. Data communication via an edge port can be based on Ethernet and via an inter-switch port can be based on the IP and/or TRILL protocol. It should be noted that control message exchange via inter-switch ports can be based on a different protocol (e.g., the IP or FC protocol).

A switch, such as switch 102, stores configuration information needed to operate switch 102 as an individual switch or as a member switch of fabric switch 100. Furthermore, switch 102 can participate in various services and operations, such as network virtualization (e.g., a virtual local area networks (VLAN)), switch partitioning, and link aggregations (e.g., a multi-chassis trunk). Furthermore, switch 102 operates on a plurality of network protocols of different network layers (e.g., Ethernet, TRILL, FC, and IP). As a result, switch 102 runs protocol daemons for each of these protocols. However, to incorporate the services and operations, the protocol daemons need to be directly modified, which can lead to conflicts and errors.

Furthermore, each of the operations, services, and the protocols is associated with one or more attributes. These attribute values (e.g., parameters) is typically applied to switch 102 when switch 102 powers up. As a result, these attribute values are stored in a persistent storage so that these values can be retrieved even when switch 102 is powered off or restarts. With existing technologies, switch 102 may store such attribute values in a local storage in an unstructured format (e.g., a string comprising the attribute values). During the boot up process, switch 102 reads and parses the attribute values in the unstructured format, and loads the attribute values into switch memory. Managing persistent storage in unstructured format is inefficient and requires runtime structuring.

To solve this problem, switch 102 is equipped with a persistent storage framework 120 which facilitates structured persistent storage to the attribute values associated with different operational units of switch 102 (e.g., modules and services of switch 102). It should be noted that other switches of network 100 can be equipped with a persistent storage framework and support persistent storage. In some embodiments, some switch of network 100 may not be equipped with a persistent storage framework. Different units of switch 102, each of which facilitates an aspect of switch 102's operations, operate on framework 120 in a structured and modular way. This allows a respective unit to be independently introduced to framework 120 in such a way that the unit can interoperate with other units (e.g., modules and services) of switch 102. Framework 120 supports MDA, OOP, and/or MVC design patterns to facilitate structured development and operation of the units in switch 102.

Since the units operate on framework 120 in a structured way, their associated attribute values can be stored in a persistent storage in a structured way. In some embodiments, framework 120 uses Object-Relational Mapping to store the attribute values of the units in a structured way in an object relational database. Framework 120 allows different classes to be defined for a unit during development based on MDA, OOP, and/or MVC design patterns. Framework 120 supports class models based on UML. In some embodiments, class models are expressed in YANG, which is a data modeling language used to model configuration and state data manipulated by NETCONF. Upon receiving class models (e.g., class name, attributes, and methods) and their relationships based on UML, framework 120 automatically generates the corresponding code, thereby ensuring structure in the operational units of switch 102.

Framework 120 seamlessly maps a respective class to a database table and vice-versa. Furthermore, framework 120 also seamlessly represents the relations among the classes (e.g., an association or a composition) in the database. As a result, when a unit becomes operational on switch 102 (e.g., when switch 102 powers up), attribute values associated with a respective class in that unit is automatically loaded from the database. Moreover, if a class changes (e.g., a new attribute or a new relationship), framework 120 seamlessly incorporates that change into the database.

Persistent Storage Framework

FIG. 1B illustrates an exemplary persistent storage framework in a switch, in accordance with an embodiment of the present invention. In this example, persistent storage framework 120 of switch 102 provides structured persistent storage to the operational units of switch 102. In some embodiments, switch 102 is coupled to an end device 114, which can operate as an administrative terminal for switch 102. Switch 102 runs one or more protocol daemons 140. For example, switch 102 can run respective protocol daemons for Ethernet, TRILL, FC, and IP. A protocol daemon facilitates the services and operations of a corresponding protocol for switch 102.

Switch 102 further includes an input interface 122 to switch 102 (e.g., a graphical user interface (GUI) and/or a command line interface (CLI). A user can access input interface 122 via end device 114. The user can obtain information from and provide instruction to switch 102 via input interface 122. Switch 102 also includes a configuration daemon 124, which can receive configuration (e.g., an IP address) for switch 102 from end device 114 (e.g., from a user) via input interface 122. Configuration daemon 124 provides this configuration information to framework 120. Framework 120 can include a configuration daemon gateway module 132, which communicates with configuration daemon 124. Upon receiving the configuration information, framework 120 can identify different attribute values (e.g., a VLAN identifier) and assigns those attribute values to the corresponding attribute of an operational unit of switch 102.

On the other hand, switch 102 can receive an instruction via input interface 122 to provide its configuration associated with one or more units. For example, a user can issue a command to show the IP addresses assigned to switch 102 from end device 114. Input interface 122 provides this instruction to configuration daemon 124, which in turn, sends an internal command to configuration daemon gateway module 132 for the requested configuration information. In response, framework 120 identifies the attributes (e.g., IP addresses) associated with the requested configuration information and obtains the corresponding attribute values (e.g., assigned IP addresses to switch 120) from a persistent storage. Configuration daemon gateway module 132 provides the obtained attribute values to configuration daemon 124. Upon receiving the attribute values, configuration daemon 124 provides the attribute values as the requested configuration information to input interface 122, which in turn, provides the configuration information to end device 114.

Framework 120 includes a core management module 130, which facilitates structured persistent storage to the attribute values associated with different operational units of switch 102 (e.g., modules and services of switch 102). Different units of switch 102 operate on core management module 130 in a structured way. This allows a respective unit to be independently introduced to framework 120 such a way that the unit can interoperate with other units (e.g., modules and services) of switch 102. Framework 120 supports MDA, OOP, and/or MVC design pattern to facilitate structured development and operation of the units in switch 102.

For example, instead of modifying protocol daemons 140, switch 102 can have plug-ins 134 for protocol daemons 140. Core management module 130 facilitates inter-operations between plug-in 134 and protocol daemons 140. Suppose that a modification to standard Ethernet protocol is needed. Instead of modifying the native protocol daemon of Ethernet, a plug-in for the protocol daemon of Ethernet can be introduced to core management module 130. Similarly, to facilitate membership to a fabric switch, fabric switch module 136 can be introduced to core management module 130. Fabric switch module 136 allows switch 102 to run a control plane with automatic configuration capability and join a fabric switch based on the control plane. Plug-ins 134 and fabric switch module 136 can be developed using MDA, OOP, and/or MVC design patterns, supported by framework 120.

Since the units of switch 102 operate core management module 130 in a structured way, their associated attribute values can be stored in a persistent storage in a structured way. In some embodiments, core management module 130 uses Object-Relational Mapping to store the attribute values of the units in a structured way in an object relational database 150. Core management module 130 allows different classes to be defined for a unit during development based on MDA, OOP, and/or MVC design patterns and expressed as a UML model, and seamlessly maps a respective class to a database table in database 150 and vice-versa.

Furthermore, core management module 130 also seamlessly represents the relations among the classes (e.g., an association or a composition) in database 150. As a result, when a unit becomes operational on switch 102 (e.g., when switch 102 powers up), attribute values associated with a respective class in that unit is automatically loaded from database 150. Moreover, if a class changes (e.g., a new attribute or a new relationship), core management module 130 seamlessly incorporates that change into database 150. It should be noted that a class defined by a user may not include explicit instructions (e.g., a Structured Query Language (SQL) query) for inserting and retrieving attribute values from database 150. The class simply includes an instruction indicating that persistent storage is required for some operations and core management module 130 facilitates the object relational mapping, and the corresponding database operations (e.g., SQL insert and select).

Attribute Data Types

To facilitate seamless object relational mapping, a persistent storage framework defines a set of data types for different categories of attributes. These attributes can be used to define class attributes of different operational units of a switch. In some embodiments, the framework can identify these class attributes expressed in a UML model. It should be noted that such expression can be represented in various forms, such as graphical, textual, XML, etc. The framework ensures these attributes are compatible with an object relational database. As a result, during operation, the framework can seamlessly map the class attributes to an object relational database and provide persistent storage to the attributes.

A data type of an attribute is basic entity provided by the framework that can be persisted or transported in the object relational database. A data type is associated with an identifier (e.g., a name). A data type can be, persisted or ephemeral, configuration or operational and read-only or read-write. The framework can serialize or de-serialize a data type to or from: XML, remote procedure call (RPC), SQL, JavaScript Object Notation (JSON), and Open vS witch Database (OVSDB) management protocol.

The framework supports different categories of attributes. Such categories include, but are not limited to, integers and numbers, string, date and time, messaging, UML relations, network, and others. In addition, the framework supports user defined data types and corresponding attributes. Table 1 includes different categories of attributes and their corresponding data types supported by the framework. It should be noted that the categories and data types listed in Table 1 is not exhaustive. The framework can support more categories and data types.

TABLE 1 Data types supported by Persistent Storage Framework Category Data Types Integers and 8-bit Unsigned Integer (UI8), 8-bit Signed Integer (SI8), Numbers UI16, SI16, UI32, SI32, UI64, SI64, 64-bit decimal (Decimal64) Vector variants of all of the above User-configured variants of all of the above UI32Range String String, StringVector, StringVectorVector, StringUC Date and Time Date, Time, DateTime Vector variants of all of the above and User-configured variants of all of the above Messaging ServiceId, ResourceId, ResourceEnum MessageType, MessagePriority, LocationId, SerializableObjectType UML Relations Association, Aggregation, Composition Network Universally Unique Identifier (UUID), World Wide Name (WWN), IPv4Address, IPv4AddressNetworkMask, IPv6Address, IPv6AddressNetworkMask, IPvXAddress, IPvXAddressNetworkMask, Uniform Resource Identifier (URI), MACAddress, MACAddress2, Host, SNMPObjectId (Simple Network Management Protocol (SNMP)) Vector variants of all of the above and User-configured variants of all of the above SQL SQLIn, SQLBetween, SQLComparator, SQLExists Other Union, Bool, BoolUC, BoolVector, SerializableObejct, SerializableObjectVector ManagedObject, ManagedObjectVector, Enumeration ObjectId, ObjectIdVector LargeObject, Map, XML

The framework provides extensive list of built-in data types, as described in conjunction with Table 1. These data types capture the attribute values (e.g., data fields) of objects. In some embodiments, the framework includes one or more attributes that provide run time introspection that allows runtime identification of classes. Since attributes can be serialized to and de-serialized from a variety of formats, the framework provides extensive support for custom behavior overriding in serialization and de-serialization. Furthermore, the framework supports user defined data types.

Object Identifier

In the example in FIG. 1B, framework 120 stores attribute values of different classes in database 150. During operation, a class is instantiated in switch 102 (e.g., in the memory of switch 102), and one or more attributes of that instance are assigned corresponding values. For example, if the class represents a line card switch 102, an attribute can be a MAC address of a port in that line card (e.g., MACAddress data type). When the line card becomes active, an instance of the class, which can be referred to as an object, is created in the memory of switch 102, and framework 120 stores the attribute values of that object in a table associated with the class in database 150.

However, a switch can have a plurality of line cards. For another line card, another object (i.e., another instance) of the class is created in the memory of switch 102, and framework 120 stores the attribute values of that other object in the table associated with the class in database 150. In this way, the same table can store attribute values of different objects of the same class. To identify different objects of a class in the table, framework 120 generates and assigns an object identifier (object ID or OID) to a respective object of a respective class. This object identifier operates as the primary identifier of that object. In the database table, this primary identifier is the primary key of that table. It should be noted that an object identifier is referred to be associated with a class in a generic sense, which indicates an object identifier of an object of the class.

FIG. 2 illustrates an exemplary object identifier generated by a persistent storage framework in a switch, in accordance with an embodiment of the present invention. During operation, an object 200 of a class is created in the memory of a switch. The persistent storage framework of the switch creates an object identifier 210 for object 200. This object identifier 210 can be the primary identifier for object 210 in the persistent storage. If the persistent storage is an object relational database, the database can include a table corresponding to the class. The attribute values of object 200 and object identifier 210 are inserted into the table. Object identifier 210 can be the primary key for that table.

In some embodiments, object identifier includes a class identifier (a class ID or CID) 220 and an instance identifier (an instance ID or IID) 230. Class identifier 220 represents the class from which the object is instantiated. In some embodiments, class identifier 220 is generated based on a hash function (e.g., Rabin Polynomial hash function) applied to the name of the class. Instance identifier 230 represents that particular instance of the object. Hence, if two objects of the same class are created, class identifier 220 of object identifier 210 remains the same for both the objects. However, the two objects differ in their respective instance identifier 230. Typically, class identifier 220 and instance identifier 230 are 32 and 64 bits long, respectively. However, these lengths can vary.

In some embodiments, instance identifier 230 includes a group identifier 232, a location identifier 234, a management module identifier 236, and a serial identifier 238. Group identifier 232 identifies a group in which the switch is a member. For example, if the switch is a member switch of a fabric switch, group identifier 232 can be a fabric switch identifier, which identifies a fabric switch. Location identifier 234 identifies the switch in the group. For example, if the switch is a member switch of a fabric switch, location identifier 234 can be a switch identifier, which identifies the switch within that fabric switch. Typically, group identifier 232 and location identifier 234 are 10 and 20 bits long, respectively.

Management module identifier 236 identifies the type of management module is operating the switch. For example, if the switch is participating in an active-standby high availability protocol (e.g., Virtual Router Redundancy Protocol (VRRP) and Virtual Switch Redundancy Protocol (VSRP)), management module identifier 236 can indicate whether the switch is an active or a standby switch. Typically, management module identifier 236 is 1 bit long. However, length of management module identifier 236 can be increased by incorporating adjacent bits from location identifier 234.

Serial identifier 238 provides identification of a specific instance of an object and can be a wrapped-around monotonically increasing number (e.g., an unsigned integer). Typically, serial identifier 238 is 32 bits long. In this way, object identifier 210 uniquely identifies an object of a class created by a management module in a switch, which can be in a fabric switch. In other words, object identifier 210 can be unique among objects, classes, management modules, fabric switches, and switch locations within a corresponding fabric switch.

Base Classes

In the example in FIG. 1B, persistent storage framework 120 maps classes to object relational tables in database 150, and inserts attribute values of an object of the class into the table. Framework 120 provides a set of base classes from which a class created for an operational unit of switch 102 can be inherited from. These base classes provide a development framework for the operational units and ensure that the operational units of switch 102 remain structured during operation. In this way, framework 120 can facilitate structured persistent storage to the attribute values of the operational units.

The framework supports a set of base classes and multiple inheritance from these base classes. FIG. 3 illustrates exemplary base classes for supporting a persistent storage framework in a switch, in accordance with an embodiment of the present invention. In some embodiments, the most base class 302 is the PersistableObject class. This class outlines the most fundamental operations supported by the persistent storage framework of a switch. Another base class 304, denoted as the ManagedObject class, is virtually derived from the PersistableObject class. Any object instantiated from an inheritance chain of the ManagedObject class can be referred to as a managed object. The framework provides seamless persistent storage support to these managed objects.

Class 304 outlines the most common attributes and operations of the objects managed by the framework. In other words, all class hierarchies derive virtually from the PersistableObject class. Since a class can inherit from multiple classes and each of these classes can inherit from the PersistableObject class, there can potentially be a conflict during execution of a managed object. This problem is generally referred to as the diamond problem. To solve this problem, the framework supports virtual derivation from the PersistableObject class. Another base class 306, denoted as the LocalManagedObjectBase class, outlines the attributes and operations locally managed within a switch. For example, a port is locally managed in a switch.

Base class 308, denoted as the LocalManagedObject class, is virtually derived from the ManagedObject class and the ManagedObjectBase class. Hence, the LocalManagedObject class outlines the attributes and operations of a switch which are locally and globally managed. For example, a port is locally managed within a switch and a VLAN configured for the port is managed globally. In some embodiments, an application (e.g., a protocol plug-in) running on a switch can specify more base classes for that application. Typically, base classes are not directly mapped to the tables of the object relational database. These base classes provide object relational mapping support. The attributes (i.e., the data fields) of these classes become part of a respective managed object derived from these base classes. As a result, the managed objects can share states and behavior.

In some embodiments, the attributes of a managed object can be any of the attribute data types supported by the framework, as described in conjunction with Table 1. The framework also supports vector variants (e.g., arrays and lists) for a number of the data types. Furthermore, the framework provides support to check whether a particular attribute is user configured. As described in conjunction with FIG. 3, the framework supports hierarchical managed objects based on inheritance. The framework also supports weak and strong references to objects. A weak reference does not protect the referenced object from being destroyed (e.g., by a garbage collector), unlike a strong reference, which protects the object from being destroyed.

Object Relational Mapping

In some embodiments, a persistent storage framework of a switch supports, both one-to-one and one-to-many, association, aggregation, and composition UML relationships. Association and aggregation are supported via ObjectID and ObjectIDVector data types, and ObjectIDAssociation and ObjectIDAssociationVector attributes, respectively. On the other hand, composition is supported via ManagedObectPointer and ManagedObectPointerVector data types and corresponding attributes. In some embodiments, the framework supports smart pointers and vector to facilitate seamless development.

FIG. 4A illustrates an exemplary UML model of classes of a switch with a persistent storage framework, in accordance with an embodiment of the present invention. In this example, a class 404, denoted as the Node class, represents network nodes, such as a switch or a router. Attributes for the Node class includes a NodeID, which represents an identifier for a node. Since a switch can be a member of a switch group (e.g., a fabric switch), the Node class has a relationship with class 402, denoted as the SwitchGroup class, which represents a group of switches. A switch can be in one such switch group and a switch group aggregates a plurality of switches. Hence, the relationship between the Node class and the SwitchGroup class is a one-to-many aggregation, which is denoted as “isMemberOf.” In this relationship, the SwitchGroup class can be referred to as the container class since a switch group “contains” a switch. On the other hand, the Node class can be referred to as a related class.

Similarly, a switch can include one or more line cards. Hence, the Node class has a relationship with class 406, denoted as the LineCard class, which represents a line card. A line card can be in one switch and a switch includes (i.e., is composed of) a plurality of line cards. Hence, the relationship between the Node class and the LineCard class is a one-to-many composition, which is denoted as “includes.” On the other hand, a switch typically has a power source, which may not be inside of the switch. So, the Node class has a relationship with class 408, denoted as the PowerSource class, which represents a power source of a node. Suppose that, at a time, a power source can power one switch and a switch can receive power from one source. Hence, the relationship between the Node class and the PowerSource class is a one-to-one association, which is denoted as “getsPower.”

A power source can be based on alternating current (AC) or direct current (DC). So, class 408-A, denoted as the ACPowerSource class, and class 408-B, denoted as the DCPowerSource class, are derived from the PowerSource class. The ACPowerSource class and the DCPowerSource class represent AC and DC power sources, respectively. Hence, based on the getsPower association, a Node can get power from a generic power source, an AC power source, or a DC power source. In this UML diagram, since the relationship between the Node class and class 408 is one-to-one, an object of the Node class can have only one of the power sources. In this example, the PowerSource class, the ACPowerSource class, and the DCPowerSource class can be referred to as the inheritance chain of the PowerSource class (class 408).

The framework can receive the UML diagram of FIG. 4A and generate the corresponding classes in a supported programming language (e.g., C++, Java, C#, etc). Furthermore, the framework generates an object relational table for the classes in the model. Furthermore, the framework can generate corresponding auxiliary tables to represent one-to-many relationships, as well as tables for classes in an inheritance chain (e.g., class derivations) and for their corresponding instances (i.e., objects), as described in conjunction with FIGS. 4C and 4D. In some embodiments, the framework receives XML representation of classes and their relationship (e.g., from a user), and generates the corresponding classes and tables. FIG. 4B illustrates an exemplary XML representation of a class corresponding to a switch with a persistent storage framework, in accordance with an embodiment of the present invention. In this example, XML definition 400 represents the Node class (class 404 of the UML model in FIG. 4A). XML definition 400 represents class Node as a ManagedObject with name “Node.”

XML definition 400 includes a respective attribute, such as NodeID, and its type (i.e., data type, as described in conjunction with Table 1). XML definition 400 also includes one-to-one and one-to-many relationships for which the Node class is a container class. For example, a node contains line cards. Hence, XML definition 400 specifies aggregation “includes” as an attribute, its type, and the class to which Node is related. It should be noted that the isMemberOf relationship is not represented in XML definition 400 even though the isMemberOf relationship to the Node class. This is because the container class for the isMemberOf relationship is the SwitchGroup class. Hence, the isMemberOf relationship is represented in an XML definition corresponding to the SwitchGroup class (not shown in FIG. 4B).

Persistent Storage in a Switch

Upon receiving XML definitions associated with the classes of a UML model, the framework creates a respective table for a respective class, their derivations, their instances (i.e., objects), and their one-to-many relationships in an object relational database. FIG. 4C illustrates exemplary tables generated by a persistent storage framework in a switch, in accordance with an embodiment of the present invention. During operation, the persistent storage framework of the switch generates a table 420 for the Node class in an object relational database. Table 420 includes a column 421 for an object identifier associated with the Node class. Column 421 includes two columns 422 and 423 for class identifier and instance identifier, respectively, of the object identifier associated with the Node class.

Table 420 also includes a column for a respective attribute of the Node class. For example, table 420 includes a column 424 for a NodeID of the Node class. Furthermore, since the Node class has a one-to-one association with the PowerSource class, for which the Node class is the container class, the framework includes a column 425 for an object identifier of an object of the PowerSource class (i.e., an object associated with the PowerSource class). Column 425 includes two columns 426 and 427 for the class identifier and instance identifier, respectively, of the object identifier associated with the PowerSource class. The framework also creates a table 410 for the PowerSource class, comprising column 411 for the object identifier associated with the PowerSource class. Column 411 includes two columns 412 and 413 for the class identifier and instance identifier, respectively, of the object identifier of the PowerSource class.

Similarly, the framework also creates a table 440 for the ACPowerSource class, comprising column 441 for an object identifier of an object of the ACPowerSource class (i.e., an object associated with the ACPowerSource class). Column 441 includes two columns 442 and 443 for the class identifier and instance identifier, respectively, of the object identifier associated with the ACPowerSource class. In the same way, the framework also creates a table 450 for the DCPowerSource class, comprising column 451 for an object identifier of an object of the PowerSource class. Column 451 includes two columns 452 and 453 for the class identifier and instance identifier, respectively, of the object identifier associated with the DCPowerSource class.

In some embodiments, the framework creates auxiliary tables to enforce consistency on columns 426 and 427. For example, the framework creates an auxiliary table 430 for the derivations of the PowerSource class (e.g., based on the UML model in FIG. 4A). In this example, table 430 corresponds to the PowerSource, ACPowerSource, and DCPowerSource classes. Table 430 includes a column 431 for the class identifier associated with the derivations of the PowerSource class. Similarly, the framework creates an auxiliary table 460 for the objects instantiated from the derivations of the PowerSource class. In this example, table 460 corresponds to the PowerSource, ACPowerSource, and DCPowerSource classes. Table 460 includes a column 461 for the instance identifiers of the objects instantiated from the derivations of the PowerSource class.

When a class identifier is generated for any class of the inheritance chain of the PowerSource class, that class identifier is inserted into table 430. The framework identifies the PowerSource, the ACPowerSource, and the DCPowerSource classes of the inheritance chain of the PowerSource class from the UML model in FIG. 4A and generates class identifiers 432, 433, and 434, respectively. The framework then inserts class identifiers 432, 433, and 434 into table 430. In this example, an entry in a table is denoted with dotted lines. Column 431 of table 430 provides consistency enforcement to column 426 of table 420 (denoted with a dashed arrow). In some embodiments, consistency enforcement of column 426 is based on a foreign key constraint on column 431 of table 430. On the other hand, when the framework identifies an object of the PowerSource, ACPowerSource, or the DCPowerSource class, the framework generates a corresponding object identifier and inserts the object identifier into table 410, 440, or 450, respectively.

When an object identifier is inserted into table 410, 440, or 450, the instance identifier of the object identifier is concurrently inserted into table 460 (denoted with dotted arrow). Suppose that, upon detecting an object in the memory of the switch, the framework inserts an object identifier comprising a class identifier 432 and instance identifier 435 into table 410. Similarly, an object identifier comprising a class identifier 433 and instance identifier 444, and an object identifier comprising a class identifier 433 and instance identifier 445 are inserted into table 440. An object identifier comprising a class identifier 434 and instance identifier 454 is inserted into table 450. The framework ensures that instance identifiers 435, 444, 445, and 454 are also inserted into table 460. Column 461 of table 460 provides consistency enforcement to column 426 of table 420 (denoted with a dashed arrow). In some embodiments, consistency enforcement to column 427 is based on a foreign key constraint on column 461 of table 460.

During operation, an object of the Node class is instantiated in the memory of the switch. The framework identifies the object in the memory and generates an object identifier for the object comprising a class identifier 464 and an instance identifier 465. The framework identifies the attribute values of the object, which includes NodelD 466 and an object identifier of a power source object. Suppose that the power source for the switch is an AC power source, and the object identifier comprises a class identifier 433 and an instance identifier 444, as stored in table 440 corresponding to the ACPowerSource class. The framework creates an entry in table 420 by inserting class identifier 464, instance identifier 465, NodeID 466, class identifier 433, and instance identifier 444 into table 420. Since consistency is enforced on columns 426 and 427, the relational database ensures that class identifier 433 and instance identifier 444 appear in columns 431 and 461, respectively.

However, even though the Node class is related to the LineCard class, since it is a one-to-many relationship, table 420 does not include an object identifier associated with the LineCard class. The framework creates an auxiliary table to represent the relationship the Node class and the LineCard class. FIG. 4D illustrates an exemplary table representing a one-to-many association, which is generated by a persistent storage framework in a switch, in accordance with an embodiment of the present invention. Upon detecting the LineCard class in the UML model in FIG. 4A, the persistent storage framework of the switch generates a table 470 for the LineCard class in an object relational database. Table 470 includes a column 471 for an object identifier associated with the LineCard class. Column 471 includes two columns 472 and 473 for corresponding class identifier and instance identifier, respectively, of the object identifier associated with the LineCard class.

During operation, an object of the LineCard class is instantiated in the memory of the switch. The framework identifies the object in memory and generates an object identifier comprising a class identifier 474 and an instance identifier 475 for the object. The framework then creates an entry in table 470 by inserting the object identifier into table 470. Similarly, the framework generates an object identifier comprising a class identifier 474 and an instance identifier 476 for another object of the LineCard class, and a third object identifier comprising a class identifier 474 and an instance identifier 477 for an object of the LineCard class. The framework creates respective entries in table 470 by inserting these object identifiers into table 470.

In some embodiments, the framework creates an auxiliary table 480 to represent the one-to-many “includes” relationship between the Node class and the LineCard class. In the relationship, the Node class is the container class and the LineCard class is the related class. Table 480 includes a column 481 for an object identifier associated with the Node class, and a column 484 for an object identifier associated with the LineCard class. Column 481 includes two columns 482 and 483 for the class identifier and instance identifier, respectively, of the object identifier associated with the Node class. Similarly, column 484 includes two columns 485 and 486 for the class identifier and instance identifier, respectively, of the object identifier associated with the LineCard class.

Suppose that the object of the Node class, which is associated with class identifier 464 and instance identifier 465, includes two line cards. Hence, the object of the Node class include two objects (e.g., an ManagedObjectVector) of the LineCard class. Suppose that instance identifiers 475 and 476 belong to these two objects. As a result, the framework inserts class identifier 464, instance identifier 465, class identifier 474, and instance identifier 475 into table 480. The framework also inserts class identifier 464, instance identifier 465, class identifier 474, and instance identifier 476 into table 480. In this way, the relationship between the object of the Node class (associated with instance identifier 465) and two objects of the LineCard class (associated with instance identifier 475 and 476) is stored in table 480.

In some embodiments, similar to tables 430 and 460, the framework creates auxiliary table 490 for the derivations of the Node class (e.g., based on the UML model in FIG. 4A). In this example, table 490 corresponds to the Node class (and its derivations, if any). Table 490 includes a column 491 for the class identifier associated with the derivations of the Node class. Similarly, the framework creates an auxiliary table 492 for the objects instantiated from the derivations of the Node class. In this example, table 492 corresponds to the Node class (and its derivations, if any). Table 492 includes a column 493 for the instance identifiers of the objects instantiated from the derivations of the Node class.

In the same way, the framework creates auxiliary table 495 for the derivations of the LineCard class (and its derivations, if any). Table 495 includes a column 496 for the class identifier associated with the derivations of the LineCard class. Similarly, the framework creates an auxiliary table 497 for the objects instantiated from the derivations of the LineCard class. In this example, table 497 corresponds to the LineCard class (and its derivations, if any). Table 497 includes a column 498 for the instance identifiers of the objects instantiated from the derivations of the LineCard class.

When a class identifier is generated for the Node class or the LineCard class, that class identifier is inserted into table 490 or 495, respectively. The framework inserts class identifiers 464 and 474 associated with the Node and the LineCard classes, respectively, into tables 490 and 495, respectively. In this example, an entry in a table is denoted with dotted lines. Column 491 of table 490 provides consistency enforcement to column 482 of table 480 (denoted with a dashed arrow). In some embodiments, consistency enforcement of column 482 is based on a foreign key constraint on column 491 of table 490. In the same way, column 496 of table 495 provides consistency enforcement to column 485 of table 480 (denoted with a dashed arrow). In some embodiments, consistency enforcement of column 485 is based on a foreign key constraint on column 496 of table 495.

On the other hand, when the framework identifies objects of the Node or the LineCard class, the framework generates a corresponding object identifier and inserts the object identifier, comprising a class identifier and an instance identifier, into table 420 or 470, respectively. When an object identifier is inserted into table 420 or 470, the instance identifier of the object identifier is concurrently inserted into table 492 or 497, respectively (denoted with dotted arrow). For example, when the framework inserts an object identifier comprising a class identifier 464 and instance identifier 465 into table 420, instance identifier 465 is inserted into table 492. In the same way, when the framework inserts an object identifier comprising a class identifier 474 and instance identifier 475 into table 470, instance identifier 475 is inserted into table 497.

Similar to table 480, the framework also creates an auxiliary table to represent the one-to-many “isMemberOf” relationship between the Node class and the SwitchGroup class, as described in conjunction with FIG. 4A. That table includes a column for an object identifier associated with the container class, which is the SwitchGroup class, and a column for an object identifier associated with the related class, which is the Node class. The column for the object identifier associated with the SwitchGroup class includes two columns corresponding to class identifier and instance identifier, respectively, of the object identifier. Similarly, the column for the object identifier associated with the Node class includes two columns corresponding to class identifier and instance identifier, respectively, of the object identifier.

It should be noted that the framework distinguishes between a composition relationship (e.g., “includes” in FIG. 4A) and an aggregation relation (e.g., “isMemberOf” in FIG. 4A). In some embodiments, for a composition relationship, the class definition of the container class includes an attribute of data type ManagedObject (and/or ManagedObjectPointer), as described in conjunction with Table 1. If the relationship is one-to-many, the date type can be ManagedObjectVector (and/or ManagedObjectPointerVector). In this way, when an object of the container class is instantiated, the related objects are created and included in that instantiated object of the container class. On the other hand, for an aggregation relationship, the class definition of the container class includes an attribute of data type ObjectId. If the relationship is one-to-many, the date type can be ObjectIdVector. In this way, the objects are created separately, and when an object of the container class is instantiated, only references to those related objects are included in that instantiated object of the container class.

Operations of a Persistent Storage Framework

FIG. 5A presents a flowchart illustrating the process of a persistent storage framework of a switch generating auxiliary tables for an inheritance chain in a structured persistent storage, in accordance with an embodiment of the present invention. During operation, the framework identifies a respective class of a non-base class inheritance chain (operation 502). The framework generates a respective class identifier for a respective identified class (operation 504). The framework generates an auxiliary table for the classes of the inheritance chain comprising a column for the class identifiers of the inheritance chain (operation 506) and updates the table for the classes of the inheritance chain by inserting the generated class identifiers (operation 508). The framework also generates an auxiliary table for the objects (i.e., the instantiated objects) of the classes of the inheritance chain, each comprising a column corresponding to the instance identifiers associated with the classes of the inheritance chain (operation 510).

FIG. 5B presents a flowchart illustrating the process of a persistent storage framework of a switch generating class tables in a structured persistent storage, in accordance with an embodiment of the present invention. During operation, the framework identifies a non-base class and generates a class table for the identified class (operation 532). In some embodiments, the framework identifies the class, and the attributes and operations (e.g., data members and methods) of the class from a class model (e.g., a UML model). The framework can receive the UML model from a graphical or textual input (e.g., a GUI, CLI, or XML file). In some embodiments, the table is named based on a hash function (e. g., a Rabin Polynomial hash function) calculated on the name of the class. The table can also have a prefix “T.” For example, if the name of the class is Node and hash(“Node”)=xxx, the table name can be Txxx. The framework adds a column comprising columns for a class identifier and an instance identifier to the class table for an object identifier (operation 534), as described in conjunction with FIG. 4C.

The framework identifies an attribute of the identified class (operation 536). It should be noted that the relationships for which the class is a container class are can also be attributes, as described in conjunction with FIG. 4A. The framework then checks whether the attribute is a simple attribute (e.g., not a relationship) (operation 538). If the attribute is a simple attribute, the framework adds a column for the identified attribute to the class table (operation 540). If the attribute is not a simple attribute (e.g., an attribute representing a relationship), the framework checks whether the attribute corresponds to a one-to-one relationship (operation 544). If the attribute corresponds to a one-to-one relationship, the framework adds a column, which is for an object identifier, comprising columns for class identifier and instance identifier of the object identifier (operation 546), as described in conjunction with FIG. 4C.

The framework enforces consistency on the class identifier and the instance identifier based on the corresponding auxiliary tables of the related classes (operation 548), as described in conjunction with FIG. 4C. In some embodiments, the consistency is enforced based on a foreign key constraint. If the attribute does not correspond to a one-to-one relationship (i.e., corresponds to a one-to-many relationship), the framework generates an auxiliary table for the one-to-many relationship (operation 550) and enforce consistency on object identifiers in the auxiliary table for the one-to-many relationship (operation 552). Upon adding a column for the identified attribute (operation 540), enforcing consistency on the class identifier and the instance identifier (operation 548), or enforcing consistency on the object identifier (operation 552), the framework checks whether all attributes have been checked (operation 542). If not, the framework continues to identify an attribute of the identified class (operation 536).

FIG. 5C presents a flowchart illustrating the process of a persistent storage framework of a switch generating an auxiliary table representing an one-to-many relationship in a structured persistent storage, in accordance with an embodiment of the present invention. Operations described in FIG. 5C elaborates operation 550 of FIG. 5B. During operation, the framework generates an auxiliary table for the one-to-many relationship (operation 562). In some embodiments, the name of the auxiliary table is based on the container table name, related table name, and the relationship name. For example, if the container table name is Txxx, related table name is Tyyy, and the relationship name is ABC, the name of the auxiliary table can be TxxxABCTyyy.

The framework adds a column for an object identifier comprising columns for class identifier and instance identifier of the container class (operation 564), as described in conjunction with FIG. 4D. The framework enforces consistency on the object identifier (i.e., both the class identifier and the instance identifier) of the container class based on the corresponding columns of the container class table (operation 566). Similarly, the framework adds a column for an object identifier comprising columns for class identifier and instance identifier of the related class (operation 568), as described in conjunction with FIG. 4D. The framework enforces consistency on the object identifier (i.e., both the class identifier and the instance identifier) of the related class based on the corresponding columns of the related class table (operation 570).

FIG. 5D presents a flowchart illustrating the process of a persistent storage framework of a switch updating tables in a persistent storage, in accordance with an embodiment of the present invention. During operation, the framework monitors the memory of the switch for object generation of the inheritance chain (operation 582) and checks whether a new object has been detected (operation 584). If a new object has not been detected, the framework continues to monitor the memory of the switch (operation 582). If a new object has been detected, the framework generates an object identifier comprising a class identifier and an instance identifier for the new object (operation 516). The frame creates an entry comprising the object identifier in the table of a class associated with the object (i.e., the class from which the object has been instantiated) (operation 588). The framework creates an entry comprising the class identifier, instance identifier, or both in corresponding auxiliary tables associated with the object (operation 590) and continues to monitor the memory of the switch (operation 582).

Distributed Configuration Management

In the example in FIG. 1A, network 100 can be a switch group (e.g., an Ethernet fabric switch). Under such a scenario, network 100 can also be referred to as switch group 100. In some embodiments, a switch group is a fabric switch. FIG. 6A illustrates an exemplary network with persistent storage framework and distributed configuration management support, in accordance with an embodiment of the present invention. In this example, switch 102, which is in switch group 100, can be configured by logging in to switch 102 using a management IP address (MIPA) 632 via a management port 602. Management port 602 can be an edge port, which is used for communicating configuration and control traffic. Switch 102 may not use management port 602 for data traffic. A user (e.g., an administrator) can use an end device 612 to log in to switch 102 based on management IP address 632 (e.g., using telnet via network 620). Switch 102 can also be configured via a console port (e.g., an RS-232 port) 604, which couples an end device 614 (e.g., a workstation). The user can access an input interface (e.g., a textual or graphical interface) of switch 102 from end device 612 or 614.

With existing technologies, a respective switch in switch group 100 is configured individually and the configuration process is repeated for a respective switch in switch group 100. Such configuration can be related to network virtualizations, partitions, and switch groups, and a plurality of network protocols of different network layers. The attribute values (e.g., parameters) of the configuration are applied to a respective switch, such as switch 102 (e.g., loaded to the switch modules, such as the processing hardware of switch 102). This process is repeated for switches 101, 103, 104, and 105. This process can be repetitive, tedious, and error-prone (e.g., human errors, such spelling mistake).

Furthermore, some of the configuration information is applicable for entire switch group 100 (e.g., a VLAN for switch group 100). Such configuration can be referred to as global configuration. This global configuration is repeated for a respective switch in switch group 100. This can lead to inconsistency among the global configuration in different switches in switch group 100. For example, the user repeats global configuration for switch 101, 102, 103, 104, and 105 in switch group 100. The user may, mistakenly, configure VLAN 110 in switch 102 and VLAN 111 in switch 101. As a result, traffic belonging to VLAN 110 may be erroneously dropped at switch 101.

To solve this problem, one of the switches in switch group 100 is elected as a principal switch, which manages and distributes configuration information in switch group 100. Suppose that switch 102 is elected as the principal switch. In some embodiments, a respective switch in switch group 100 broadcasts its information in switch group 100, and the switch with the lowest (or highest) identifier value is elected as the principal switch. Other switches of switch group 100, such as switches 101, 103, 104, and 105, can be referred to as managed switches. When the user accesses switch 102 (e.g., via end device 112 or 114), switch 102 allows the user to configure the global configuration of switch group 100. Switch 102, in turn, provides that global configuration to switches 101, 103, 104, and 105. Furthermore, switch 102 also allows the user to configure switches 101, 103, 104, and 105 in the switch group. Switch 102, in turn, provides the corresponding local configuration information to switches 101, 103, 104, and 105, respectively.

In some embodiments, a respective switch of switch group 100 is equipped with a persistent storage framework, as described in conjunction with FIG. 1B. The framework stores the configuration information, comprising both local and global configuration information, in a local persistent storage, which can be an object relational database. For example, in switch 102, framework 120 stores the configuration information in object relational database 150. The configuration information is loaded from database 150 to the switch modules (e.g., the ASIC chips of switch 102). Framework 120 maintains the global configuration of switch group 100 in database 150. Framework 120 also maintains respective local configuration of a respective switch, including switch 102, of switch group 100 in database 150. Switch 102 then provides a copy of database 150 to switches 101, 103, 104, and 105, each of which in turn, stores that copy in its object relational database. In this way, a respective switch in switch group 100 has the same local and global configuration. This allows a user to access the configuration of switch group 100 from any member switch.

Since switch 102 can also be accessed via console port 604 via end device 614, the user can configure switches of switch group 100 without the presence of a management network. It should be noted that, even though a user can configure the switches of switch group 100 from principal switch 102, the user can obtain the local configuration information of a respective switch of switch group 100 via any of the member switches of the switch group. For example, switch 101 can be accessed by logging in to switch 101 using a management IP address 631 via a management port 606. The user can use an end device 616 to log in to switch 101 based on management IP address 631. Since switch 101 includes the configuration information in object relational database 640 of switch 101, the user can obtain the global configuration information as well the local configuration information of a respective switch of switch group 100 from switch 101.

In some embodiments, switch group 100 is associated with a virtual IP address 610. During operation, virtual IP address 610 is associated with the principal switch of switch group 100. As a result, the user can access principal switch of group 100 via virtual IP address 610 without knowing the management IP address 632. Furthermore, if switch 102 becomes unavailable (e.g., due to a failure), another switch in switch group 100, such as switch 101, is elected as the principal switch and virtual IP address 610 becomes associated with switch 101. Since switch 101 has the configuration information in database 640 is the same as the configuration information in database 150, switch 101 can continue to facilitate distributed configuration for the switches of switch group 100. As a result, the user can continue to access the principal switch of switch group 100, which is switch 101, via virtual IP address 610 and configure the switches of switch group 100.

In some embodiments, a respective switch in switch group 100 is associated with an internal control IP address (ICIPA), which is used for communication among member switches of switch group 100. For example, an internal control IP address can be used for communication via an inter-switch port. When the principal switch of a switch group provides the configuration information to a managed switch, the principal switch communicates with that managed switch based on respective internal control IP addresses. Suppose that internal control IP addresses 621 and 622 are associated with switches 101 and 102, respectively. When switch 102 provides the configuration information to switch 101, switch 102 uses IP addresses 621 and 622 as the destination and source addresses for the packets comprising the configuration information.

In some embodiments, a respective switch in a switch group can receive configuration information from a user. FIG. 6B illustrates an exemplary switch group with multi-input and multi-principal switch support, in accordance with an embodiment of the present invention. In this example, switches 101, 102, 103, 104, and 105 are associated with management IP addresses 631, 632, 633, 634, and 635, respectively. A user can provide configuration information to a respective switch (e.g., via a console of the switch) in switch group 100 by logging in to that switch using the corresponding management IP address via a management port. For example, a user can log in to switch 103 using management IP address 633 and provides configuration information 664. Configuration information 664 can be global configuration information associated with switch group 100 or local configuration information associated with any of the member switches. Similarly, the user can log in to switch 101 using management IP address 633 and provides configuration information 662.

Suppose that configuration information 662 and 664 can cause a conflict in the switch. For example, configuration information 662 and 664 can be associated with conflicting quality of service settings for switch 105. If both switches 101 and 103 are allowed to operate as a principal switch, switches 101 and 103 can individually apply these conflicting configurations to switch 105. This can lead to race condition in switch group 100. To solve this problem, a switch group internally has one principal switch, and other switches forward their received configuration information to that principal switch. That principal switch receives the configuration information, serializes them, resolves any conflict, and applies them based on distributed commit. In this way, it would appear to the user that the switch group is being configured from any of the member switches, though internally, the switch group is configured from the principal switch.

For example, switches 101 and 103 forward configuration information 662 and 664, respectively, to principal switch 102 of switch group 100. Switch 102 receives configuration information 662 and 664, and serializes them (e.g., based on the order of arrival or an associated priority). In some embodiments, if switch 102 detects any conflict, switch 102 resolves the conflict based on its serialization. For example, configuration information 664 is serialized before configuration information 662, switch 102 resolves the conflict by applying the configuration of configuration information 664 to switch 105 based on distributed commit, and discarding configuration information 662. In this way, it would appear to the user that switch 105 is being configured switches 101 and/or 103, though internally, switch 102 configures switch 105.

In some embodiments, in switch group 100, different member switch can be the principal switch for different services. A service can be a modular component which manages a related set of configuration. In the example in FIG. 1B, a plug-in can correspond to a service. A principal switch manages all global and local configuration information of the service the switch is associated with. Suppose that switches 101 and 102 are principal switches for port management and network virtualization, respectively. As a result, in switch group 100, switch 101 processes all global and local configuration information associated with port management, and switch 102 processes all global and local configuration information associated with network virtualizations. In some embodiments, switches in switch group 100 elect a principal switch for a respective service. The election process can be based on load balancing such that different services are associated with different principal switches.

During operation, a user logs in to switch 102 using management IP address 632 and provides configuration information 666, which is associated with port management (e.g., creating a port channel). Even though switch 102 is a principal switch, switch 102 forwards configuration information 666 to switch 101 since switch 101 is the principal switch for port management. On the other hand, suppose that configuration information 662 is associated with network virtualization (e.g., creating a new VLAN). Even though switch 101 is a principal switch, switch 101 forwards configuration information 662 to switch 102 since switch 102 is the principal switch for network virtualization.

Interoperability of Software Versions

In the example in FIG. 6A, when principal switch 102 receives update information (e.g., setting up VLAN 110 for switch group 100) from a managed switch, switch 102 synchronizes that update information with a respective switch of switch group 100. A respective switch, in turn, applies the update information. Applying the update information includes loading the update information to the switch modules, and storing it in the persistent storage of a respective switch of switch group 100.

FIG. 7A illustrates an exemplary switch group with persistent storage framework and multiple software versions, in accordance with an embodiment of the present invention. In this example, switches of switch group 100 have two different software versions—versions 1 and 2. Here, switch version 2 is the updated version. It should be noted that a switch group can include more than two software versions as well. Switches 101 and 103 have software version 1, and switches 102, 104, and 105 have software version 2. Similar to switch 101, switch 102 includes the configuration information in an object relational database 150, as described in conjunction with FIG. 1B.

Typically, member switches of switch group 100 have the same software version (e.g., either software version 1 or 2). This allows information from one switch to be synchronized with other member switches. If a switch has an upgraded software version, the switch leaves the switch group until other switches are upgraded as well. As a result, switches 101 and 103 may not be in the same switch group as switches 102, 104, and 105. This is because an attribute field can be different for different software versions. For example, if principal switch 102 tries to synchronize that different value of the attribute field with switch 101, an inconsistency can occur. Hence, a software version upgrade may not be performed gradually while keeping a respective member switch operational in switch group 100. This leads to unavailability and reduced operational capability of switch group 100.

To solve this problem, a respective member switch of switch group 100 uses a portable representation (e.g., an XML representation) to synchronize its update information. The information in a portable representation is recognizable by principal switch 102 of switch group 100. Since both local and global configuration of switch group 100 is replicated at a respective member switch, to ensure interoperability, principal switch 102 synchronizes attribute values of different software versions. Suppose that nodeID of class Node in FIG. 4A is of type UI16 in software version 1 and of type string in software version 2, as described in conjunction with Table 1. If a user issues a user command to update nodeID at switch 101, which has software version 1, the user provides the nodeID as an integer. Switch 101 represents this update information using a portable representation, includes the portable representation in a notification message, and sends the notification message to principal switch 102.

Upon receiving the notification message, principal switch 102 extracts the portable presentation from the message and obtains the integer value of the nodeID from the portable representation. Principal switch 102 creates a respective instruction to update the corresponding attribute (i.e., the nodeID of switch 101) with the received integer value for software versions 1 and 2 in the switch group. In some embodiments, this instruction is an SQL transaction executable in the persistent storages of the switches with the corresponding software version. For software version 1, the instruction can be an SQL transaction executable in database 640. Since the received nodeID is compatible with software version 1, principal switch 102 can directly incorporate the received nodeID in the instruction for software version 1.

However, since the received value is an integer and the nodeID in software version 2 is a string, principal switch 102, if supported, converts the nodeID from integer to a string. If not supported, principal switch 102 can use a default value for the string. Principal switch 102 incorporates the converted nodeID (i.e., the nodeID string) in the instruction for software version 2. Principal switch sends the instruction for software version 1 to switches 101 and 103, and the instruction for software version 2 to switches 102, 104, and 105. In this way, the configuration information of a respective member switch, even with different software versions 1 and 2, remains synchronized. As a result, both local and global configuration of switch group 100 is replicated at a respective member switch, even with a different software version, of switch group 100.

In some embodiments, the instructions from principal switch 102 are executed in a distributed commit. During operation, principal switch 102 creates a respective instruction to prepare the update information (e.g., an SQL transaction) for software versions 1 and 2 in the corresponding persistent storage, and sends the instruction for software version 1 to switches 101 and 103, and the instruction for software version 2 to switches 102, 104, and 105. A respective managed switch receives the instruction for the local software version, prepares the update information (e.g., the SQL transaction) specified in the instruction in a local persistent storage, and acknowledges the preparation (e.g., with a corresponding transaction identifier).

Upon receiving an acknowledgement from a respective managed switch, principal switch 102 sends an instruction to a respective switch (including the local switch) to commit the transaction in the local persistent storage (e.g., database 640 in switch 101 and database 150 in switch 102) and the local switch modules (e.g., switch ASICs). If one of the switches does not acknowledge the preparation, the transaction is not executable in that switch, and hence, cannot be synchronized in switch group 100. Under such a circumstance, principal switch 102 instructs the managed switches with a successful preparation to roll back the transaction.

It should be noted that, to ensure interoperability, a member switch with the most updated software version (e.g., version 2) is elected as the principal switch of switch group 100. In some embodiments, a principal switch is selected based on a priority value. The member switches with the most updated software version is configured with (e.g., automatically or by a user) a higher priority value than the member switches with an older software version. In the example in FIG. 7A, the priority value of switches 102, 104, and 105 is higher than switches 101 and 103. If a switch group has a set of switches with the same highest priority value, the switch with the lowest (or highest) switch identifier value in the set is elected as the principal switch. In the example in FIG. 7A, since switches 102, 104, and 105 has the same priority value, switch 102 can be selected as the principal switch if it has the lowest (or highest) switch identifier value.

FIG. 7B illustrates exemplary XML representations of update information for multiple software versions, in accordance with an embodiment of the present invention. In this example, XML definition 722 represents the portable representation of update information of an object of the Node class (class 404 of the UML model in FIG. 4A) for software version 1. On the other hand, XML definition 732 represents the portable representation of update information of an object of the Node class for software version 2. In some embodiments, if switch 101 or 103 receives update information of an object of the Node class from a user command, that switch sends XML definition 722 to principal switch 102. On the other hand, if switch 104 or 105 receives update information of an object of the Node class, that switch sends XML definition 732 to principal switch 102.

XML definitions 722 and 732 include values for a respective attribute, such as nodeID, of the Node class. XML definitions 722 and 732 also include one-to-one and one-to-many relationships for which the Node class is a container class, as described in conjunction with FIG. 4B. If the attribute values of an object of the Node class in switch 101 of FIG. 7A is updated, switch 101 uses XML definition 722 as the portable representation, which comprises the updated values of the attributes of the object. Suppose that the object is updated with a new identifier, a new power source, and a new line card (e.g., a new object of the Node class is created). XML definition 722 then includes identifier 724, which is an integer, an object 726 of the PowerSource class, and an object 728 of the LineCard class.

Suppose that, in software version 2, attribute type of the nodeID is of type string and the power source type is of AC power source (e.g., an object of the ACPowerSource class). Hence, if a switch with software version 2, such as switch 104 of FIG. 7A, receives update information comprising the attribute values of an object of the Node class from a user command, switch 104 uses XML definition 732 as the portable representation, which comprises the updated values of the attributes of the object. Suppose that the object is updated with a new identifier, a new power source, and a new line card. XML definition 732 then includes identifier 734, which is a string, an object 736 of the ACPowerSource class, and an object 728 of the LineCard class (this attribute type remains the same for both software versions).

Synchronization Management

As described in conjunction with FIG. 6A, suppose that switch 102 has been elected the principal switch of switch group 100. During switch group formation, switch 102 manages configuration information of a respective managed switch in switch group 100. FIG. 7C illustrates an exemplary synchronization management among switches with different software versions, in accordance with an embodiment of the present invention. Database 150 of switch 102 includes a table 420-2, which is the table instance of table 420 in FIG. 4C for software version 2. Similarly, database 640 of switch 101 includes a table 420-1, which is the table instance of table 420 for software version 1.

In switch group 100, a respective switch can receive update information (e.g., update to local or global configuration information), as described in conjunction with FIG. 6B. During operation, switch 101 receives update information (operation 751). This update information can be for one or more attribute values in table 420-1. Switch 101 generates a portable representation of the received update (operation 752). In some embodiments, the portable representation is an XML representation, as described in conjunction with FIG. 7B. Switch 101 then sends the portable representation to switch 102 (operation 753). Switch 101 can include the portable representation in a notification message (e.g., in the payload of a message of a notification service of switch group 100) and send the notification message comprising the portable representation to switch 102.

Upon receiving the portable representation, switch 102 converts the attribute values in the portable representation to corresponding attribute values of a respective software version, as described in conjunction with FIG. 7A (operation 754). Using the corresponding converted values, switch 102 generates a respective instruction to prepare respective target update information (e.g., an SQL transaction) expressed for a respective software version (e.g., for software versions 1 and 2) (operation 755). Switch 102 sends the instruction for a software version to the switches with that software version. A respective managed switch receives the instruction corresponding to the local software version, prepares the update information in a local persistent storage, and acknowledges the preparation. For example, switch 102 sends the instruction to prepare the update information expressed for software version 1 to switch 101 in its persistent storage (operation 756). Switch 101 receives the instruction, prepares a transaction with update information in database 640 (operation 757), and, upon a successful preparation, acknowledges the preparation (e.g., with a corresponding transaction identifier) (operation 758).

Switch 102 receives acknowledgement from a respective managed switch (operation 759). Switch 102 then determines that the transaction is prepared at a respective switch and ready to be committed. Switch 102 sends an instruction to a respective switch (including the local switch) to commit the transaction in respective local persistent storage and switch modules. For example, switch 102 sends an instruction to switch 101 to commit the transaction (operation 760). Upon receiving the instruction, switch 101 commit the transaction in the local database (i.e., in table 420-1 of database 640) and switch modules (operation 761).

Operations

FIG. 8A presents a flowchart illustrating the synchronization process of a managed switch with persistent storage framework, in accordance with an embodiment of the present invention. During operation, the switch receives an update to the configuration information (operation 802). The switch can receive this configuration information from a user command. A user can issue the command locally (e.g., via a command line interface command) or remotely (e.g., via telnet, or NETCONF), as described in conjunction with FIG. 6B. The switch then generates a portable representation of the update information (operation 804). Examples of a portable representation include, but are not limited to, XML and JSON. FIG. 7B illustrates an example of such portable representation in XML format.

The switch creates a notification message comprising the portable representation (operation 806). This notification message can be a message of a notification service of a switch group in which the switch is a member. The switch encapsulates the notification message in a fabric encapsulation and sets the identifier of the principal switch as the egress switch identifier or the encapsulation header (operation 808). The identifier of the principal switch can be one or more of: a MAC address, an RBridge identifier, and an IP address. The switch then identifies an egress port associated with the identifier of the principal switch (e.g., from a local forwarding table) and transmits the notification message via the identified port (operation 810).

FIG. 8B presents a flowchart illustrating the synchronization process of a principal switch with persistent storage framework, in accordance with an embodiment of the present invention. During operation, the switch receives a notification message comprising portable representation from a managed switch (operation 832). The switch then obtains the update information in the portable representation from the notification message (operation 834) and determines the different software versions of the switch group (operation 836). The switch can maintain a mapping (e.g., in a table) between the switch identifier of a switch and its software version for a respective member switch of a switch group. For example, switch 102 in FIG. 7A maintains a mapping between a switch identifier of switch 101 and its software version 1. The switch can determine the software versions of the switch group from such a mapping.

The switch generates an instruction message instructing to prepare the persistent storage for the update information expressed for a respective identified software version (operation 838). In some embodiments, the switch uses different namespace to maintain a copy of the same class in a respective software version. Based on that copy, the switch generates the instruction for the corresponding software version. The switch identifies the switch(es) of one of the identified software versions (e.g., from the mapping) (operation 840) and sends the corresponding instruction message to a respective identified switch (operation 842). The switch checks whether it has sent the instruction for all software versions (operation 844). If not, the switch identifies the switch(es) of another identified software versions (operation 840) and sends the corresponding instruction message to a respective identified switch (operation 842). In some embodiments, the switch prepares the update information in the local persistent storage as well.

Upon sending the instruction for all software versions, the switch receives a response from a respective managed switch (operation 846) and checks whether all persistent storages have been prepared (operation 848). If all persistent storages have not been prepared (i.e., one or more switches have not prepared the persistent storage, for example, due to a failure), the switch rolls back the configuration information from the local persistent storage (operation 850). The switch then generates a control message instructing to roll back the configuration information from the persistent storage and sends the message to a respective successful managed switch (i.e., a switch with successful storage preparation) (operation 852). In other words, the switch may not send the control message to the managed switches which have not succeeded in preparing their corresponding local persistent storage.

If all persistent storages have been prepared, the switch generates a control message instructing to commit the configuration information to the persistent storage and the switch modules, and sends the message to a respective switch (operation 854). It should be noted that a respective switch also includes the local switch, wherein the switch instructs the local switch to commit the configuration information. Commit refers to finalizing information (i.e., ending the current transaction and making the configuration information permanent) in the switch modules or in the persistent storage. By checking whether all persistent storages have been prepared (operation 848), the switch determines whether the configuration information is eligible for a distributed commit in the switch group. If the switch determines eligibility, the switch instructs the managed switches to commit. This process can be referred to as a distributed commit.

FIG. 8C presents a flowchart illustrating the process of a principal switch generating update information for a target software version for the synchronization process, in accordance with an embodiment of the present invention. The operations described in conjunction with FIG. 8C correspond to operation 838. During operation, the switch determines the target software version of the target managed switch(es) (i.e., the switch(es) for which the principal switch is generating the instruction, as described in conjunction with FIG. 8B) (operation 862). The switch checks whether a version conversion is needed (operation 864). A version conversion is needed for the switches with a different software version than the principal switch. In the example in FIG. 7A, when switch 102 generates an instruction to prepare a transaction, a version conversion is not needed if the instruction is generated for switch 104 and 105, but is needed for switches 101 and 103.

If a version conversion is needed, the switch then determines a namespace for the determined software version (operation 866) and obtains the class chain associated with the update information in the determined namespace (operation 868). In some embodiments, the namespace is a programming language namespace. Examples of such namespace include, but are not limited to, C++, Java, C#, Python, and PHP namespace. In the example in FIG. 7A, switch 102 can use the global or default namespace for software version 2 and include the class definitions of software version 1 in a different namespace. A class chain can include all related classes. For example, if an object of the PowerSource class is updated, the corresponding objects of Node class should also be updated. The switch then instantiate the class in the local memory (operation 870). In some embodiments, the switch uses the class chain loaded in the memory to generate the target update information (e.g., to determine the attribute types of the target update information). It should be noted that, if a version conversion is not needed, the class chain is already loaded in the memory.

If a version conversion is not needed (operation 864) or the class chain has been instantiated (operation 870), the switch assigns values to the unchanged attributes in the target update information (i.e., the update information expressed for the target software version) (operation 872). The switch then identifies an attribute type difference (e.g., between an integer and a string) with the originating software version of the originating switch (i.e., the switch which has originated the portable representation) (operation 874). In the example in FIG. 7A, if switch 102 receives a portable representation from switch 101, switch 102 would not identify an attribute difference when the target managed switches are switches 101 and 103. The switch checks then whether a type conversion is supported for the attribute type difference (operation 876). Such type conversion can be supported by the persistent storage framework, as described in conjunction with FIG. 1B.

If a type conversion is supported, the switch converts the value of the corresponding attribute type in the update information to the target attribute type and include in the target update information (operation 878). The target attribute type is the corresponding attribute type in the software version of the target managed switch(es). Suppose that, in the example in FIG. 7B, attribute nodeID is of type UI16 in XML definition 722 and a target attribute type of nodeID is of type string. If a type conversion is supported, upon receiving XML definition 722, switch 102 converts the value of identifier 724, which is an integer, to a string. If a type conversion is not supported, the switch assigns a default value to the target attribute type and include in the target update information (operation 880). The switch checks whether all attribute type difference has been determined (operation 882). If not, the switch continues to identify another attribute type difference with the originating software version of the originating switch (operation 874).

If all attribute type difference has been determined, the switch assigns a default value to the attributes which are not present in the originating software version (i.e., the software version of the switch originating the portable representation) (operation 884). In the example in FIG. 7A, if software version 1 is the originating software version, software version 2 may not have an attribute specified in the portable representation based on software version 1. The switch then includes the assigned value(s) in the target update information (operation 886). The switch generates an instruction with the target update information (e.g., with the unchanged, converted, and default attribute values) expressed for the target software version (operation 888). In some embodiments, this instruction is an SQL transaction. This instruction with the target update information is inserted in the instruction message of operation 838.

Exemplary Switch

FIG. 9 illustrates an exemplary switch with a persistent storage framework and interoperability with multiple software versions, in accordance with an embodiment of the present invention. In this example, a switch 900 includes a number of communication ports 902, a packet processor 910, a persistent storage module 930, a synchronization module 932, and a storage device 950. Switch 900 can also include switch modules 960 (e.g., processing hardware of switch 900, such as its ASIC chips), which includes information based on which switch 900 processes packets (e.g., determines output ports for packets). Packet processor 910 extracts and processes header information from the received frames. Packet processor 910 can identify a switch identifier associated with the switch in header of a packet.

In some embodiments, switch 900 maintains a membership in a switch group, as described in conjunction with FIG. 1, wherein switch 900 also includes a switch group module 920. Switch group module 920 maintains a configuration database in storage device 950 that maintains the configuration state of every switch within the fabric switch. Switch group module 920 maintains the state of the fabric switch, which is used to join other switches. In some embodiments, switch 900 can be configured to operate in conjunction with a remote switch as an Ethernet switch.

Communication ports 902 can include inter-switch communication channels for communication within the fabric switch. This inter-switch communication channel can be implemented via a regular communication port and based on any open or proprietary format. Communication ports 902 can also include one or more extension communication ports for communication between neighbor fabric switches. Communication ports 902 can include one or more TRILL ports capable of receiving frames encapsulated in a TRILL header. Communication ports 902 can also include one or more IP ports capable of receiving IP packets. An IP port is capable of receiving an IP packet and can be configured with an IP address. Packet processor 910 can process TRILL-encapsulated frames and/or IP packets.

During operation, persistent storage module 930 stores configuration information associated with the switch group in a table, which includes one or more columns for attribute values of the configuration information, in object relational database 940 in storage device 950. If switch 900 is a principal switch, synchronization module 932 obtains update information from a portable representation, which is extracted from a notification message received via one of communication ports 902. The update information includes a first set of attribute values for a first table (i.e., a first data structure) in database 940. Synchronization module 932 then identifies a software version of a second switch in the switch group and generates an update instruction instructing to update the first table in a persistent storage in the second switch with the target update information. It should be noted that the software version of the second switch can be the same as switch 900, and the first and second sets of attribute values can be the same.

Synchronization module 932 can identify the software version of the remote switch from a mapping between an identifier of the remote switch and the software version. In some embodiments, switch 900 also includes a conversion module 970, which converts a first attribute value to a second attribute value (e.g., from an integer to a string). Conversion module 970 assigns a default attribute value to an attribute in the target update information (e.g., if conversion is not supported or for attributes without a value specified in the portable representation).

In some embodiments, synchronization module 932 verifies whether the target update information is prepared for storage in a persistent storage of a respective switch of the switch group. If the update information is prepared, synchronization module 932 generates an instruction message instructing to commit the target update information to the persistent storage and switch modules of a respective switch of the switch group. If the update information is not prepared, synchronization module 932 rolls back the target update information from a persistent storage of a switch, which has succeeded in storage preparation, of the switch group.

If switch 900 is a managed switch, synchronization module 932 identifies update information from a received user command. The update information comprises a first set of attribute values for a first table in database 640. Synchronization module 932 generates a portable representation, which is recognizable by the principal switch of the switch group, of the update information. Synchronization module 932 also generates a notification message comprising the portable representation. This notification message is destined for the principal switch. In some embodiments, synchronization module 932 verifies whether the update information is prepared for storage in the local persistent storage. If the update information is prepared, synchronization module 932 generates an acknowledgement message comprising a transaction identifier associated with the preparation.

Note that the above-mentioned modules can be implemented in hardware as well as in software. In one embodiment, these modules can be embodied in computer-executable instructions stored in a memory which is coupled to one or more processors in switch 900. When executed, these instructions cause the processor(s) to perform the aforementioned functions.

In summary, embodiments of the present invention provide a first switch and a method which supports multiple software versions in a switch group. In one embodiment, the first switch includes one or more ports, a switch group module, a persistent storage module, and a synchronization module. The switch group module maintains a membership in a switch group. The switch group includes a plurality of switches and operates as a single switch. The persistent storage module stores configuration information associated with the switch group in a table, which includes one or more columns for attribute values of the configuration information, in a local persistent storage. The synchronization module obtains update information from a portable representation. This update information comprises a first set of attribute values for a first data structure in the persistent storage. The synchronization module identifies a software version of a second switch in the switch group and generates an update instruction to update the first data structure in a persistent storage in the second switch with target update information. The target update information comprises a second set of attribute values updated from the first set of attribute values.

The methods and processes described herein can be embodied as code and/or data, which can be stored in a computer-readable non-transitory storage medium. When a computer system reads and executes the code and/or data stored on the computer-readable non-transitory storage medium, the computer system performs the methods and processes embodied as data structures and code and stored within the medium.

The methods and processes described herein can be executed by and/or included in hardware modules or apparatus. These modules or apparatus may include, but are not limited to, an application-specific integrated circuit (ASIC) chip, a field-programmable gate array (FPGA), a dedicated or shared processor that executes a particular software module or a piece of code at a particular time, and/or other programmable-logic devices now known or later developed. When the hardware modules or apparatus are activated, they perform the methods and processes included within them.

The foregoing descriptions of embodiments of the present invention have been presented only for purposes of illustration and description. They are not intended to be exhaustive or to limit this disclosure. Accordingly, many modifications and variations will be apparent to practitioners skilled in the art. The scope of the present invention is defined by the appended claims. 

What is claimed is:
 1. A first switch, comprising: one or more ports; switch group circuitry configured to maintain a membership in a network of interconnected switches, wherein the network of interconnected switches is identified by a fabric identifier; synchronization circuitry configured to: obtain update information from a portable file format, wherein the update information comprises a first set of attribute values for a first data structure in a persistent storage of the first switch; identify a software version of a second switch in the network of interconnected switches; determine target update information for the second switch based on the software version of the second switch, wherein the target update information includes the update information in a representation compatible with the software version of the second switch; and generate an update instruction comprising the target update information to update a second data structure in a persistent storage in the second switch using the target update information, wherein the second data structure includes one or more rows for corresponding attribute values of the target update information.
 2. The first switch of claim 1, wherein the software version of the second switch is different than a software version of the first switch.
 3. The first switch of claim 1, wherein the synchronization circuitry is further configured to identify the software version of the second switch from a mapping between an identifier of the second switch and the software version of the second switch.
 4. The first switch of claim 1, wherein the synchronization circuitry is further configured to: verify whether the target update information is prepared for storage in a persistent storage of a respective switch of the network of interconnected switches; and in response to verifying that the update information is prepared, generate an instruction message instructing to commit the target update information to respective persistent storage of a respective switch of the network of interconnected switches.
 5. The first switch of claim 4, wherein, in response to verifying that the target update information is not prepared, the synchronization circuitry is further configured to roll back the target update information from a persistent storage of a respective switch, which has succeeded in storage preparation, of the network of interconnected switches.
 6. The first switch of claim 1, further comprising a conversion circuitry configured to convert a first attribute value to a second attribute value to determine the target update information, wherein the first attribute value is of a first attribute type, and wherein the second attribute value is of a second attribute type.
 7. The first switch of claim 1, further comprising a conversion circuitry configured to assign a default attribute value to an attribute in the target update information.
 8. The first switch of claim 1, wherein the persistent storage is an object relational database, and wherein a data structure in the persistent storage is a table in the database.
 9. The first switch of claim 1, wherein the portable file format is based on one or more of: Extensible Markup Language (XML) and JavaScript Object Notation (JSON).
 10. The first switch of claim 1, wherein the network of interconnected switches is a fabric switch, wherein the plurality of switches included the network of interconnected switches operate as a single switch.
 11. A first switch, comprising: one or more ports; switch group circuitry configured to maintain a membership in a network of interconnected switches, wherein the network of interconnected switches is identified by a fabric identifier; synchronization circuitry configured to: identify update information from a received user command, wherein the update information comprises a first set of attribute values for a first data structure in a persistent storage of the first switch; generate a portable file format comprising the received update information; and generate a notification message comprising the portable file format, wherein the notification message is destined to a second switch in the network of interconnected switches; and persistent storage circuitry configured to store target update information in the first data structure, wherein the target update information is obtained from an instruction message received from the second switch, and wherein the target update information includes the update information in a representation compatible with a software version of the first switch.
 12. The first switch of claim 11, wherein the synchronization circuitry is further configured to: verify whether the target update information is prepared for storage in the persistent storage; and in response to verifying that the target update information is prepared, generate an acknowledgement message comprising a transaction identifier associated with the preparation, wherein the acknowledgement message is destined to the second switch.
 13. The first switch of claim 11, wherein the portable file format is based on one or more of: Extensible Markup Language (XML) and JavaScript Object Notation (JSON).
 14. A method, comprising: maintaining a membership of a first switch in a network of interconnected switches, wherein the network of interconnected switches is identified by a fabric identifier; obtaining update information from a portable file format, wherein the update information comprises a first set of attribute values for a first data structure in a persistent storage of the first switch; identify a software version of a second switch in the network of interconnected switches; determining target update information for the second switch based on the software version of the second switch, wherein the target update information includes the update information in a representation compatible with the software version of the second switch; and generating an update instruction comprising the target update information to update a second data structure in a persistent storage in the second switch using the target update information, wherein the second data structure includes one or more rows for corresponding attribute values of the target update information.
 15. The method of claim 14, wherein the software version of the second switch is different than a software version of the first switch.
 16. The method of claim 14, further comprising identifying the software version of the second switch from a mapping between an identifier of the second switch and the software version of the second switch.
 17. The method of claim 14, further comprising: verifying whether the target update information is prepared for storage in a persistent storage of a respective switch of the network of interconnected switches; and in response to verifying that the update information is prepared, generating an instruction message instructing to commit the target update information to respective persistent storage of a respective switch of the network of interconnected switches.
 18. The method of claim 17, further comprising, in response to verifying that the target update information is not prepared, rolling back the target update information from a persistent storage of a switch, which has succeeded in storage preparation, of the network of interconnected switches.
 19. The method of claim 14, wherein determining the target update information comprises converting a first attribute value to a second attribute value, wherein the first attribute value is of a first attribute type, and wherein the second attribute value is of a second attribute type.
 20. The method of claim 14, further comprising assigning a default attribute value to an attribute in the target update information.
 21. The method claim 14, wherein the persistent storage is an object relational database, and wherein a data structure in the persistent storage is a table in the database.
 22. The method of claim 14, wherein the file format representation is based on one or more of: Extensible Markup Language (XML) and JavaScript Object Notation (JSON).
 23. The method of claim 14, wherein the network of interconnected switches is a fabric switch, wherein the plurality of switches included the network of interconnected switches operate as a single switch.
 24. A method, comprising: maintaining a membership of a first switch in a network of interconnected switches, wherein the network of interconnected switches is identified by a fabric identifier; identifying update information from a received user command, wherein the update information comprises a first set of attribute values for a first data structure in a persistent storage of the first switch; generating a portable file format comprising the received update information; generating a notification message comprising the portable file format, wherein the notification message is destined to a second switch in the network of interconnected switches; and storing target update information in the first data structure, wherein the target update information is obtained from an instruction message received from the second switch, and wherein the target update information includes the update information in a representation compatible with a software version of the first switch.
 25. The method of claim 24, further comprising: verifying whether the target update information is prepared for storage in the persistent storage; and in response to verifying that the target update information is be prepared, generating an acknowledgement message comprising a transaction identifier associated with the preparation, wherein the acknowledgement message is destined to the second switch.
 26. The method of claim 24, wherein the portable file format is based on one or more of: Extensible Markup Language (XML) and JavaScript Object Notation (JSON). 